coinos-ui.git/src/routes/(app)/send/lightning/[payreq], branch master

send: explain duplicate submits instead of reporting a routing failure

2026-10-02T14:10:15Z

Resubmitting an invoice that was already paid, is still in flight, or is awaiting reconciliation came back as the generic "failed to route" error, which reads as if the payment never went out. Map those server responses to specific messages with a link to the payment history. Co-Authored-By: Claude Opus 5.5

send: stop the Max buttons from cancelling their own submit, show LNURL action errors

2026-09-22T02:41:39Z

Choosing Max on the LNURL-pay page left the button spinning forever. Two things combined: The Max buttons set `loading` from their click handler. Svelte flushes `disabled={loading}` to the DOM before the browser runs the button's submit activation, and a disabled button submits nothing. Set loading from the form's onsubmit instead, the way the Send button always did. The /ln page never passed `form` into the Lnurlp and Lnurlw components, so any action failure (pay, max or withdraw) rendered nothing and never reset the spinner. Pass it through, and reset loading when a result arrives. Verified in headless Chrome against the dev stack: the bolt11 Max lands on the fee view, and the LNURL Max surfaces the server's error and re-enables the buttons. Co-Authored-By: Claude Fable 5.1

send: quote the lightning routing fee up front and add Max to lightning sends

2026-09-22T02:21:43Z

The lightning send page now asks the server what the payment will cost before showing the Send button: the exact routing fee from the route query, the platform fee, and the total. The quoted fee is submitted as the maxfee, so what the user sees is what gets debited; advanced settings still let them override it, and if the quote fails the page falls back to the old 2% reserve. Max on the amount step asks the server for the largest amount whose amount + routing fee + platform fee lands exactly on the balance, and for an offer picks up the invoice fetched for that exact amount. LNURL-pay gets a Max button too. The invoice only exists once we name an amount, so the action fetches a probe invoice at the ceiling, lets the server solve for the amount, then fetches the real invoice for it. Co-Authored-By: Claude Fable 5.1

bolt12 zaps: accept offers in send flow, show/publish user offer

2026-07-30T15:51:45Z

- parse lno= from BIP-321 bitcoin: URIs; send page parses offers for preview now that /parse handles them - settings/nostr shows the user's standing lno1 offer with copy/QR and a button to publish it as a kind 10058 offer list for NIP-177 zaps - new locale strings translated Co-Authored-By: Claude Fable 5

fix: rename hidden maxfee field to fee to match form handler

2026-02-15T08:17:44Z

Co-Authored-By: Claude Opus 4.6

increase default maxfee

2025-12-10T23:50:40Z

display locked balance

2025-05-12T19:36:18Z

fix maxfee

2025-02-12T20:31:36Z

change maxfee param name

2025-02-05T23:18:13Z

capture ln comments

2025-01-25T18:50:51Z